fix(cli): Open a session without a default schema - #1825

Thank you for the fix.

--query reports success when a statement fails. Console::runOnce catches the error, prints Query failed: ... and returns false; runMultiple stops; run() is void, so main falls through to return 0. This predates the change and holds for every catalog — --query "select * from nonexistent" against tpch exits 0 today — but the change routes one more failure into it. A bare table name against a schemaless catalog used to abort during runner.initialize() with a non-zero exit; now it is an ordinary failed statement that a script cannot detect. runOnce already returns the bool; passing it up through runMultiple and run() would let main exit non-zero.

The hint prints in non-interactive runs. Console::run gates its greeting on interactive and gates live progress on isatty(STDERR_FILENO), with the comment that the non-interactive paths opt in via --show_live_progress — the convention being that --query and piped stdin emit query output and nothing else. The new message is printed from main before any of that is known, so every scripted run against a schemaless catalog carries it. Could it move to where the mode is known and follow the greeting?

Thank you — the exit-code table in the description and the scrut cases make this easy to check.

One behaviour I want to make sure is intended: a failed --init statement now returns before the interactive branch, so the prompt never appears. For a scripted run that is clearly right. For an interactive one the user has already seen Query failed: ..., and --init can be expensive — generating data, creating tables — so exiting costs them the whole setup rather than dropping them at a prompt where they can look around and fix it. Would reporting the failure and still opening the REPL be better there?